VersionX (basic versioning addon)

• • ☆ A M B ☆
  • 3,141 Posts
  Mark Hamstra Reply #21, 15 years, 9 months ago

  DEMO
  Here’s the details for the demo:
  
  markhamstra.nl/dev/versioning/manager/
  
  User: Curious
  Pass: iwanttoknow
  
  Components -> VersionX (modExt) for the modExt version
  Components -> VersionX (modExt) -> VersionX for the plain table version.
  
  
  
  Right now, the modExt version has the looks, but not yet the functionality of the plain table one (compare, view details etc). I’m no longer working on the plain one any more, but for as long as I don’t yet show the same functions using modExt it’ll be available so you can atleast have a look. It’s most likely packed with bugs
  
  I’m taking slow steps into the realm of modExt and the next step is adding a context menu to get access to a modal window where you can view the details or compare a revision with another one for that resource.
  
  I thought I’d share the link with you now, even if there’s no real functionality to try out.. This will remain available for probably until I release the alpha (which has at least the functionality I mentioned above and probably most in the first post of this topic).. Aiming for next week or begin January.
  
  
  
  (And yes: I deliberately disabled access to anything included resources for the time being on that login.)
  Mark Hamstra • Developer spending his days working on Premium Extras and a MODX Site Dashboard with the ability to remotely upgrade MODX and extras to make the MODX world a little better.
  
  Tweet me @mark_hamstra, check my infrequent blog at markhamstra.com, my slightly more frequent ramblings at MODX.today or see code at Github.
• • ☆ A M B ☆
  • 3,141 Posts
  Mark Hamstra Reply #22, 15 years, 9 months ago

  You can now view the revision info in the modExt view.
  
  
  (click to view at full size)
  
  The popup uses plain tables atm to display the data, this will stay this way in the alpha release, but if someone has ideas to improve this view, I’d love to take this into the beta / public release.
  
  You can view how it is now in the Demo
  Mark Hamstra • Developer spending his days working on Premium Extras and a MODX Site Dashboard with the ability to remotely upgrade MODX and extras to make the MODX world a little better.
  
  Tweet me @mark_hamstra, check my infrequent blog at markhamstra.com, my slightly more frequent ramblings at MODX.today or see code at Github.
• • 
  • 1,613 Posts
  fourroses666 Reply #23, 15 years, 9 months ago

  just some idea, some area where u can select fields u like to backup, standard backup content field, but things like longtitle isn’t that interesting.
  Evolution user, I like the back-end speed and simplicity
• • MODX Staff
  • 730 Posts
  netProphET Reply #24, 15 years, 9 months ago

  Git doesn’t actually store deltas to track changes to files. It stores entire files and indexes them by a hash of their contents. (They call it a "dumb content tracker".)
  It just computes deltas or diffs when it needs them (eg showing diffs to the user, merging)
  I personally don’t know if storing deltas is really going to make anything easier. It may reduce the storage requirements for content that is changed frequently, but it will also add a bunch of complexity to operating on that content IMHO.
  Mike Schell
  Lead Developer, MODX Cloud
  Email: [email protected]
  GitHub: https://github.com/netProphET/
  Twitter: @mkschell
  
• • ☆ A M B ☆
  • 3,141 Posts
  Mark Hamstra Reply #25, 15 years, 9 months ago

  @Fourroses: thanks for the idea. A system/plugin setting to determine what to store (or at least: what to show) sounds like a good idea.
  
  @netProphET: thanks for sharing your thoughts.
  
  
  Spend a lil’ while again this night (hehe) and pretty much finished the comparison window.
  
  
  
  
  Feel free to login on the demo (see first post on this page) for a live view.
  
  I started writing the VersionX Documentation and the VersionX Roadmap on the RTFM.
  
  A little background info for those interested...
  The Fields & Settings tab simply fetches all fields for the two revisions, except content, and checks if they are similar. If they’re not, they are returned to the script and show up in the grid.
  
  The Content tab uses a different approach, as it goes line by line using xpdorevisioncontrol.
  
  Whereas the fields & settings tab is not influenced by updates to the core / xPDO, the content one is relying on the revisioncontrol class of xpdo. Right now that class returns a plain string according to some standard I think I understand for the most part which is being exploded and parsed appropriately. When that class, or the way it outputs information, change, this part of the component will probably break.
  I’d expect this class to be used by the core devs for the core versioning/workflow scheduled for 3.0, so yeah, just a mental note to keep an eye on this to see if it has been improved when time goes by.
  Mark Hamstra • Developer spending his days working on Premium Extras and a MODX Site Dashboard with the ability to remotely upgrade MODX and extras to make the MODX world a little better.
  
  Tweet me @mark_hamstra, check my infrequent blog at markhamstra.com, my slightly more frequent ramblings at MODX.today or see code at Github.
• • ☆ A M B ☆
  • 3,141 Posts
  Mark Hamstra Reply #26, 15 years, 9 months ago

  After a holiday break... news!
  
  Managed to get the restore function working properly.
  
  
  Which means I’m close to releasing an alpha package.
  
  Things still to do before the release:
  - Clean up the code and folders
  - Use more lexicon strings throughout the code to allow translations
  
  I’ve got a busy week, but funny enough those are the weeks I can focus on projects like these the most.
  
  
  If I’m going to give you guys an ETA, it’d be coming week. Of course no promises - but should be accurate
  Mark Hamstra • Developer spending his days working on Premium Extras and a MODX Site Dashboard with the ability to remotely upgrade MODX and extras to make the MODX world a little better.
  
  Tweet me @mark_hamstra, check my infrequent blog at markhamstra.com, my slightly more frequent ramblings at MODX.today or see code at Github.
• • ☆ A M B ☆
  • 3,141 Posts
  Mark Hamstra Reply #27, 15 years, 9 months ago

  While the actual code is ready... I’m having trouble packing it all up in a package.
  
  On top of that, I have a *really* busy week coming up with several important deadlines, and the one after may be busy also.
  
  If I haven’t found a few spare hours to work on this before the 24th, it should be no problem to release it in that week.
  
  
  
  Sorry I had good hopes to release this soon, but it’s just meant to be!
  Mark Hamstra • Developer spending his days working on Premium Extras and a MODX Site Dashboard with the ability to remotely upgrade MODX and extras to make the MODX world a little better.
  
  Tweet me @mark_hamstra, check my infrequent blog at markhamstra.com, my slightly more frequent ramblings at MODX.today or see code at Github.
• • 
  • 24,544 Posts
  BobRay Reply #28, 15 years, 9 months ago

  FWIW, I think the best example for packaging is in the _build directory of Shaun’s Login add-on: https://github.com/splittingred/Login
  
  Basically, it creates the category, then adds the snippets and chunks to the category so they get saved automatically and puts in two file resolvers, one for the core and one for assets. You can comment out the parts you don’t need.
  If you run into trouble, just ask here.
  Did I help you? Buy me a beer
  Get my Book: MODX:The Official Guide
  MODX info for everyone: http://bobsguides.com/modx.html
  My MODX Extras
  Bob's Guides is now hosted at A2 MODX Hosting
  
• • ☆ A M B ☆
  • 3,141 Posts
  Mark Hamstra Reply #29, 15 years, 9 months ago

  Thanks Bob - I’ll have a look at that one when I’ve got some time again.
  
  My main source was the Quip addon and some tutorial somewhere. The Login one seems much more straightforward from a first glance, thanks.
  Mark Hamstra • Developer spending his days working on Premium Extras and a MODX Site Dashboard with the ability to remotely upgrade MODX and extras to make the MODX world a little better.
  
  Tweet me @mark_hamstra, check my infrequent blog at markhamstra.com, my slightly more frequent ramblings at MODX.today or see code at Github.
• • ☆ A M B ☆
  • 3,141 Posts
  Mark Hamstra Reply #30, 15 years, 9 months ago

  Good news!
  
  Alpha is here!
  
  And the code is on Github!
  
  
  Please find the transport package in the attachment. It is currently pending in the Repository. Approved! http://modxcms.com/extras/package/?package=792
  
  Known bug:
  - Restoring a revision does not work.. this problem started occuring after starting to use a connector.php file in the assets folder instead of directly posting to the processor in the core folder... The getlist and comparing resources work fine, but I’m having the idea some security measure is preventing the restoreRevision processor to save changes. If anybody has an idea or could look into it, that would be greatly appreciated.
  
  
  As said, the code is on Github, thanks to the help of Romain Tripault! Chapeau, Romain!
  
  
  Please report bugs, improvements and feature requests on Github. Before filing a feature request, please see if it’s already on the Roadmap.
  
  Also translations can be posted as a pull request on Github.
  
  
  
  Related links:
  Documentation: http://rtfm.modx.com/display/ADDON/VersionX
  Roadmap: http://rtfm.modx.com/display/ADDON/VersionX.Roadmap
  In Development topic: http://modxcms.com/forums/index.php/topic,58889.20.html
  VersionX on my personal website: http://www.markhamstra.nl/modx/addons/versionx.html
  Commercial support / bounties: business at markhamstra.nl
  
  Mark Hamstra • Developer spending his days working on Premium Extras and a MODX Site Dashboard with the ability to remotely upgrade MODX and extras to make the MODX world a little better.
  
  Tweet me @mark_hamstra, check my infrequent blog at markhamstra.com, my slightly more frequent ramblings at MODX.today or see code at Github.

This discussion is closed to further replies. Keep calm and carry on.