Jiwa 8

[pricerc]

I've noticed that our invoices from Jiwa over the past several months appear to be generated from a Jiwa 8 instance, complete with pretty flag for the currency.

How far away is it from being suitable for Jiwa partners to start "dogfooding" for internal use ?

[Mike.Sheen]

I've noticed that our invoices from Jiwa over the past several months appear to be generated from a Jiwa 8 instance, complete with pretty flag for the currency.

How far away is it from being suitable for Jiwa partners to start "dogfooding" for internal use ?

I think we are ready now. We've been using it ourselves for about 6 months - but it's only the last month or so that we've settled things down enough to be able to support others using it also.

We'll want to formalise the best way to support you in case there are problems in upgrading your existing data, and the process of how we manage critical hotfixes if they are needed - so I'll ask our team to reach out to you with the details.

[pricerc]

Thanks Mike.

We're not currently using Jiwa for "production", so existing data isn't a problem.

We do quite a lot of trans-tasman business, so we decided on holding out for the multi-currency support.

[Mike.Sheen]

Thanks Mike.

We're not currently using Jiwa for "production", so existing data isn't a problem.

We do quite a lot of trans-tasman business, so we decided on holding out for the multi-currency support.

Alright, so I need not have created this page then!

Just open a ticket on our helpdesk to obtain a licence for 8.0.24.0, and download the that build from the poorly named "Jiwa Version 7.0 Development Stream" tab of our downloads page.

[pricerc]

it'll still be useful.

At some point I'll want to try upgrading customer databases to assess the impacts on our library of plugins.

And I'm sure I'm not the only reseller wanting to dabble!

[Mike.Sheen]

At some point I'll want to try upgrading customer databases to assess the impacts on our library of plugins.

It would be advisable then to keep Upgrade Guidance for Plugin Developers bookmarked.

Not much requires attention - some columns and properties renamed, and if you have the motivation, any custom searches should now use the new search window - but the old one is still there and works just like it did. But you should use the new one, it's awesome.

[pricerc]

the two first entries brought a wry smile to my face.

JiwaGrid.GridText
CustomSettingValues.ItemFromSettingName

One that breaks VB code and one that breaks C# code.

So everyone can be equally offended

[Mike.Sheen]

the two first entries brought a wry smile to my face.

JiwaGrid.GridText
CustomSettingValues.ItemFromSettingName

One that breaks VB code and one that breaks C# code.

So everyone can be equally offended

Oh, I made sure some people will be more offended than others - Plugin Maintenance now has a button to convert VB.NET plugins to C#, but we don't have one going the other way.

[pricerc]

the two first entries brought a wry smile to my face.

JiwaGrid.GridText
CustomSettingValues.ItemFromSettingName

One that breaks VB code and one that breaks C# code.

So everyone can be equally offended

Oh, I made sure some people will be more offended than others - Plugin Maintenance now has a button to convert VB.NET plugins to C#, but we don't have one going the other way.

lol.

As much as I like VB, I don't blame you.

Unless I'm doing extensive XML manipulation, which VB's XML literals make easy to read, I generally choose C# over VB for new projects.

[Mike.Sheen]

lol.

As much as I like VB, I don't blame you.

Unless I'm doing extensive XML manipulation, which VB's XML literals make easy to read, I generally choose C# over VB for new projects.

It was not exactly a decision within my control - from the wiki of the library, ICSharpCode/CodeConverter that we used:

C# - VB
In most cases, if you aren't absolutely sure it's right for your situation, I wouldn't recommend moving serious production code from C# to VB en masse.

The language is a second class citizen with fewer features, tools and developers. It also has a whole collection of subtle quirks which can hide issues and make it very hard to write reliable, maintainable, performant code
Surveys show it's one of the most 'dreaded' languages.
Because of the above, there has been less demand for conversion in this direction and hence the conversion quality is worse (e.g. Recent c# features aren't well supported)

It's the last sentence that was of concern for us.