Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make slime more accessible #197

Closed
GoogleCodeExporter opened this issue Mar 25, 2015 · 9 comments
Closed

Make slime more accessible #197

GoogleCodeExporter opened this issue Mar 25, 2015 · 9 comments

Comments

@GoogleCodeExporter
Copy link

Would be nice to have instructions or whatever else is needed to make it
easy for people to use the slime checks. This would also make it more
likely that we would get new rules contributed back.

Original issue reported on code.google.com by [email protected] on 4 Oct 2008 at 10:01

@GoogleCodeExporter
Copy link
Author

+1

The question I have is whether Slime also works with the Refactoring Engine that
comes with tools or only with the tool less Refactoring Engine core. If so
instructions for loading OmniBrowser would also help. I also find the 
integration
into OmniBrowser quite unintuitive.

In the longer term better integration of Seaside into OmniBrowser would be 
cool. For
example a 'register as application' entry on the context menu of a class.

Original comment by [email protected] on 4 Oct 2008 at 10:26

  • Added labels: Platform-Squeak
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Slime should be backward compatible. It just extends the existing rule-engine 
with a few more methods. It 
shouldn't matter if you use OmniBrowser or the old Morphic UI.

Documentation can be found here:

    http://www.lukas-renggli.ch/blog/ob-rb-1
    http://www.lukas-renggli.ch/blog/ob-rb-2
    http://www.lukas-renggli.ch/blog/ob-rb-3

If you find it unintuitive please go ahead and fix it. For my own purpose I 
find it absolutely perfect.

I agree that an Seaside-OmniBrowser toolkit would be cool.

Original comment by renggli on 5 Oct 2008 at 6:50

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Linked it on the web page:
http://www.seaside.st/documentation/tools

Original comment by [email protected] on 5 Oct 2008 at 10:08

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

But none of this specifically mentions the seaside-specific rules, does it?

Original comment by [email protected] on 5 Oct 2008 at 10:36

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

http://www.lukas-renggli.ch/blog/slime

Original comment by [email protected] on 5 Oct 2008 at 10:56

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Ok... getting better. Now can we include this in the Universe and in the 
one-click
image? :)

I'd just like people to be likely to end up having it and using it.

Original comment by [email protected] on 5 Oct 2008 at 12:15

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

It is in the one-click image.

Original comment by renggli on 5 Oct 2008 at 2:29

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

The RB doesn't allow to add new categories for rules. Adding a category would 
mean to change the core 
implementation of the RB.

Original comment by renggli on 5 Oct 2008 at 9:45

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

I worked on this one. Slime is now part of Seaside and has its rules have their 
own category. Load the latest 
Refactory-Core and Seaside-Slime and Seaside-Tests-Slime. Seaside-Slime and 
Seaside-Tests-Slime are now 
part of the Seaside repository.

Accessibility can be further improved, but marked as fixed for now.

Original comment by renggli on 18 Oct 2008 at 7:24

  • Changed state: Fixed
  • Added labels: ****
  • Removed labels: ****

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant