| | | |
 Uploading ....Moving to Lasso 9- Veteran
developers carry experience forward
- Much LP8.5 code will run on
Lasso 9
- Much functionality is implemented for compatibility's
sake
- This compatibility library has source available in our
public SVN
- Will be adding to it as necessary
- We accept
contributions
- What is gone
- Security related
- File
security is gone
- Files best secured through the OS
- Previous
system was redundant and easy to goof-up
- Database/table
security is gone
- Cumbersome, unnecessary
- All
databases we work with have security
- Still have single-point
host configuration
- Many previously deprecated elements
have been removed, others still in compatibility library
- Automatic
encoding of any sort
- What has changed
- Some of
the copy semantics
- How values are stored globally
- Lasso 9
relies on FastCGI now (old connectors will not work)
- How
multiple sites are configured
- Serialization
- Dynamic local
variable names
- Differences listed <link>
- What
is the same
- Stuff that is not actually in the compatibility
lib
- Inline, action_param
- Basic methodologies
- Includes,
"pages" and how they generate content
- Many of the data
types such as strings, integers, decimals, arrays, maps, etc.
- Why
you should convert existing sites
- Moving forward
- Code
milestone
- Continue working on docs
- Heavy push to get
Windows version in parity
|
|
|
| | | |
|
Would it be a good idea to have a page with "Pitfalls" encountered with upgrading? Some of these may be bugs that will be worked out, others may be new /changed syntax, but in the meantime It would be a great help at least to me that, If I run into a problem, I have somewhere to go and see if others have run into the same problem, and how they were able to either fix it or work around it in the meantime before posting to the list.
I know I found a few things that aren't working as expected, but through help on the list was able to find a workaround until they are fixed (Like the problem with floats in MySQL).
Don't get me wrong, I'm not talking about a "bitch" page - only constructive information, with workarounds to specific problems that are likely to crop up when upgrading or writing new code. Perhaps as some of these are fixed (if they are bugs), or as they are officially entered into the proper places, they can be removed?