11/22/2024 8:55:38 AM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss suggestions, enhancements, and a wishlist for the future of slxdeveloper.com. View the code of conduct for posting guidelines.
|
|
|
|
Future development of SLX
Posted: 16 May 07 3:37 AM
|
fiogf49gjkf0d I have been using SLX v7 for just over a week, and have started to make modifications with the Architech. My background is with Sage Line 100 and Sage MMS development. For those that do not know Sage MMS (now Sage 200) is Sage's Mid Market accounting solution in the UK. It is written in C# and is highly customisable, utilising the .NET Scripting engine.
I am somewhat puzzled that Sage have not utilitied the technologies they have created for MMS/200 with other products. I feel SLX would benefit greatly from these. Downside for those experienced with SLX development, would be a complete change of development methods, but I went through that process when moving from Line 100 to MMS and think the move was well worth it.
These are just a few of my instant reactions to SLX development environment.
Regards
Steve Jowett |
|
|
|
Re: Future development of SLX
Posted: 16 May 07 12:27 PM
|
fiogf49gjkf0d SLX is moving in that same direction to all .NET based development. It is a long and slow process however. Mainly because of the years of customizations people have built on the current technology in SLX that can't be immediately dropped. We have .NET extensions now, which do leave a lot to be desired but still does provide the ability to use .NET where needed and not worry about deployment and distribution. SLX 7.2 web moves to an all .NET architecture. All code is written in C# or VB.NET, you can even use Visual Studio for development and then add your custom assemblies into SLX. The LAN client will be making that same move, but the process is a slow one - however it IS without question coming.
The current, unofficial word is that the architecture behind SLX 7.2 web is being considered for other Sage application as part of a future strategy of having better and easier integration between products and a more common playing field for Sage products.
I'm no fan of VBScript. I feel SLX development in general (in it's current state) is completely behind the times - SLX 7.2 web excluded. So the future plans for SLX can't get here fast enough as far as I am concerned  . It is on it's way. IMO the development environment and experience as a whole for SLX 7.2 web is far beyond what other similar CRM apps provide - by a long way. The app itself is growing and the front end application can be a bigger focus now that the architecture has changed to a more up to date platform with current technologies and dev standards. We'll just have to wait a bit longer to get that for windows client customization.
-Ryan |
|
|
|
Re: Future development of SLX
Posted: 17 May 07 8:13 AM
|
fiogf49gjkf0d Question: is MMS related to the old main frame package started by Software International? |
|
|
|
Re: Future development of SLX
Posted: 17 May 07 9:13 AM
|
fiogf49gjkf0d Originally posted by Robert Levine
Question: is MMS related to the old main frame package started by Software International? |
|
No, Sage MMS (which stands for Mid-Market Solution) is the successor to Sage Line 100 accounting software. Line 100 was a MS-DOS based accounting package, written in Sage's propriorty language, Retrieve 4GL. Sage had a few false starts rewriting Line 100 for Windows, including a 16 bit version for Windows 3.x and later 32bit for Win95+. These where shelved and never really had a commerical release. Later Sage release a Windows front-end to Line 100, which was no more than a windows rendering of the DOS based screens.
Finally Sage released Line 100 v8 which consisted of Sales, Purchase and Nominal Ledgers and Cash Book modules,written in C++ and had the Windows Scripting Engine embeded within it for developers use. v9 introduced Stock, POP, SOP etc, but these where no more than a windows rendering of the DOS modules.
Sage later added SOP, POP and Stock written in C# and renamed the product to Sage MMS version 2
Version 3 saw a rewrite of the Sales, Purchase and Nominal Ledger and Cash Book modules in C# and support for the .NET scripting engine.
Version 4, which has just been released saw another rename from Sage MMS to Sage 200.
Version 4.1 will include as a module, Sage CRM.
Regards
Steve Jowett |
|
|
|
Re: Future development of SLX
Posted: 19 May 07 10:32 AM
|
fiogf49gjkf0d Like Ryan says, there is a movement to consolidate the "tool sets and Technology.
At Insights "NATO" (North American Technology Office) was announced under Jim Foster. All indications are that the pioneering work done in Gobi (Slx v7.2 web) is going to be a VERY significant player.
--
rjl |
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|