Changes between Version 5 and Version 6 of PadreNextGen


Ignore:
Timestamp:
Mar 21, 2012, 11:03:07 AM (3 years ago)
Author:
azawawi
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PadreNextGen

    v5 v6  
     1[[PageOutline(2-4)]] 
     2== Padre the Next Generation IDE == 
     3 
    14I wanted to share my thoughts about how we can drive Padre in 2012. I know that we have been adding feature after feature to Padre core lately and bloat seems inevitable. You will notice how Adam cleverly added the features tab in preferences to keep the Padre startup and runtime memory cost at a minimum. However as Padre matures, we need to move into a more plugin-based architecture. Each Padre release has been growing bigger and bigger. For example: 
    25 
     
    3841}}} 
    3942 
     43== TODO == 
     44 
     45* Remove the concept of user levels (i.e. beginner mode) 
     46 
    4047== Why Padre needs Moose or something like it == 
    4148 
     
    4451== Conclusion == 
    4552How about we fix Padre to be '''minimal''' and move some of the functionality or unused features outside of Padre core. We should start working on well-thought-out '''plugin API''' that truly allows plugins to '''modify''' Padre behavior in '''every way possible'''. 
     53 
     54== References == 
     55[http://rudd-o.com/linux-and-free-software/faq-why-user-levels-are-bad-usability Why User Levels are Bad Usability]